(Item 8345) DLUR handling Locates with OCR on while LU or CP-SVR pipe is inactive ------------------------------------------------------------------------ John McGinn of AS/400 submitted the folllowing request: I am trying to determine what the criteria should be for a DLUR to send a positive response on a Locate that it receives with the OCR bit on. Assume that we have some pre-defined dependent LUs that reside on our DLUR. Should we only positively respond to search requests with the OCR bit on if the particular dependent LU has positively responded to an ACTLU from the DLUS? The real reason for my question boils down to how NNS Processing for Option Set 1116 is defined. According to the architecture, an NNS supporting this option set will delete/retain the registered resource pending the results in the Locate reply. If a DLUR is only supposed to reply positively on a search if it has successfully processed ACTLU, then this means that I cannot register dependent LUs until they have gone through this ACTLU processing (otherwise they will be deleted by the NNS upon a negative search response from the DLUR). I see this as a bad thing because I will now be forced to register only a single dependent LU at a time (since they become ACTLU'd serially). What I would really like to see is for an NNS not to delete the registered resource based upon a negative search reply. This way, a DLUR could register ALL of it's pre-defined dependent LUs once their CP-CP session with the NNS becomes active. This would be far more efficient than registering these dependent LUs one at a time and having to provide constant registration updates based upon the status change caused by ACTLUs and DACTLUs being received. Comments? Therefore, if the DLUR has a predefined or dynamically created LU for which it has received a Locate with OCR on, the DLUR should reply Found to the Locate regardless of whether the LU is active or not. It also should register the LUs right away and not wait until they are active; let the NNS turn around all of the non-OCR Locates as soon as possible, and have the DLUR reject the Locate only if the LU is not there. Because the Locate with OCR on is generated after the DLUS gave its OK to the session, the DLUR could reply Found even with the pipe down in the hope that the pipe will come back up before the BIND arrives. A Found returned by the DLUR with the pipe down cannot include a CV X'40' = DLUS since there is no current DLUS. Therefore, CV X'40' will not be included in the Found when there is no active CP-SVR pipe. Responding positively to the Locate request removes the need for the DLUR to remember which dependent SLUs it needs to re-register. It will also allow the search to be terminated at that point, instead of performing a network broadcast, subarea search, border node search, etc. It will also allow the DS database caches at CDS nodes and EBNs to retain knowledge of where the dependent LU resides. That way, when the DLUR subsequently obtains a new DLUS, network broadcast searches may be avoided.